home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr35
/
isa_0992.zip
/
ISAROUTE.ZIP
/
ROUTE.EX2
< prev
Wrap
Text File
|
1992-06-25
|
10KB
|
297 lines
The Scenario:
David, Mike and Myself live in Toronto, James and Eddie live
in Vancouver, Linda and Graham live in Halifax and Ed lives in New York.
We all wish to play ISA together, but since we live in different cities,
it would get quite expensive to have our systems calling each other. With
ISA being able to route the game files, we can all play each other and the
cost of long distance calls is cut down to only a couple of people.
David, Linda, Graham and I use our AdultNet addresses, James uses his
SigNet address, Eddie, and Ed use their FidoNet address', and Mike
uses his ImexNet address. (Remember, the Address listed in your ROUTE.CFG
file can be ANY Valid address that you have and does not have to be the
address that you have configured in your ISA.CFG).
Since mail already flows between all of our systems, we will use
the existing connections for the routing of our ISA files as well. The
following rough diagram shows the connection links between our systems:
Eddie
|
|
James
|
|
Mike ------------ Jeff ----------- Ed
|
|
David
|
|
Linda
|
|
Graham
The Valid Addresses for the above are as follows:
Jeff: 15:15/1 David: 15:100/250 James: 1:153/769
1:250/517 1:259/312 25:4604/171
34:3416/0 34:2416/0
Graham: 15:400/110
Linda: 15:400/100 Ed: 15:610/300
1:255/999 1:999/000 Mike: 10:10/11
34:999/999 15:100/206
Eddie: 1:153/709
Let's start with the 4 systems on the end of each arm of our diagram, since
they will be the easiest of the group to set up.
Eddie will be sending all routed files to James. Using the same
address that Eddie has each of the nodes configured as in his NODES.CTL,
his ROUTE.CFG file would look like this:
---------------------------- CUT HERE -----------------------------
*1:153/709
%25:4604/171
#N
?25:4604/171
?34:3416/0
?10:10/11
?1:999/000
?34:2416/0
?34:999/999
?15:400/110
---------------------------- CUT HERE -----------------------------
Notice that Eddie is using his FidoNet address as his primary
address for the game. He routes the files to James as indicated by the %
operator. He must list all of the other addresses that files will be sent
to, they do not all have to be from the same Zone (Network) as you can see
from the various addresses listed above. You can put in Any or All of a
particular nodes addresses in the list, as long as they point to at least
one valid address of the system you are trying to route files to.
Mike will be sending all of the routed files through my system. His
ROUTE.CFG file would look like this:
---------------------------- CUT HERE -----------------------------
*10:10/11
%15:15/1
#N
?15:15/1
?1:153/769
?1:153/709
?15:100/206
?15:610/300
?15:100/250
?15:400/100
?15:400/110
---------------------------- CUT HERE -----------------------------
Notice that since Mike has an AdultNet address (Zone 15) but not a
SigNet address (Zone 25-29 & 34) it's easier for him to configure most of
the nodes with AdultNet addresses. Since he doesn't have a SigNet address,
he uses James Fido Address for files destined for James' system.
Ed's situation is identical to Mike's, thus his ROUTE.CFG file will
look like this:
---------------------------- CUT HERE -----------------------------
*15:610/300
%15:15/1
#N
?15:15/1
?1:153/769
?1:153/709
?15:100/206
?15:100/206
?15:100/250
?15:400/100
?15:400/110
---------------------------- CUT HERE -----------------------------
Graham's situation is similiar in that he will be routing all files
via Linda's system, thus his ROUTE.CFG will look like this:
---------------------------- CUT HERE -----------------------------
*15:400/110
%15:400/100
#N
?15:400/100
?15:100/250
?15:15/1
?15:100/206
?15:610/300
?1:153/769
?1:153/709
---------------------------- CUT HERE -----------------------------
Since all 4 of the above systems are 'End' nodes, their routing
files are fairly straight-forward and virtually identical. As you can see,
it doesn't matter which address you use to configure a node you're playing
against, as long as it is one of the valid addresses for that particular
node.
DO NOT READ ANY FURTHER, unless you fully understand the above
examples and the examples from ROUTE.EX1.
The following 3 examples show the ROUTE.CFG files for 3 'Intermediary'
hubs in our routing scenario.
James is the 'Intermediary hub' between Eddie and myself. His
routing file will look similar to the 'hub' routing file in our ROUTE.EX1
examples. Considering our current scenario, James' ROUTE.CFG file will
look like this:
---------------------------- CUT HERE -----------------------------
*25:4604/171
%34:3416/0
#H
?34:3416/0
?10:10/11
?1:999/000
?34:2416/0
?34:999/999
?15:400/110
;
;
*1:153/769
%1:153/709
#H
?1:153/709
---------------------------- CUT HERE -----------------------------
James prefers using his SigNet address, thus in the first block, he
uses his SigNet address to forward the ISA game files from, as the list
indicates, he sends the routed files for several systems to my SigNet
address. In the second block, Eddie does not have a SigNet address, so
James uses his FidoNet address in the 'From' position. The simple 4 line
block, shows that all files addressed to Eddie's system will be sent to
Eddie. The two semi-colons used are ignored by ISA and were put in only to
simplify reading the file for this example.
Notice that James uses the Hold flag with the # (Status) operator.
Since both Eddie and I call James daily, it's much easier for him to simply
put the game files on hold for when Eddie and I call in.
Linda's situation is very similiar to James'. She needs to have
her system forward files to Graham from the rest of us. She also needs to
forward Her files and Graham's to David who is her 'Hub'. Linda's
ROUTE.CFG file would look like this:
---------------------------- CUT HERE -----------------------------
*15:400/100
%15:100/250
#N
?15:100/250
?15:15/1
?15:610/300
?15:100/206
?25:4604/171
?1:152/919
;
;
*15:400/100
%15:400/110
#H
?15:400/110
---------------------------- CUT HERE -----------------------------
Since Graham runs a private node, Linda puts all of the routed
files for him on Hold until he calls in for them. She routes everything
else to David (her hub).
David needs to route files for Linda and Graham to Linda's system
and everything else gets routed to me since I am David's 'Hub'. His
ROUTE.CFG file would look like this:
---------------------------- CUT HERE -----------------------------
*15:100/250
%15:15/1
#N
?15:15/1
?15:100/206
?15:610/300
?25:4604/171
?1:153/709
;
;
15:100/250
%15:400/100
#H
?15:400/100
?34:999/999
?1:255/999
?15:400/110
---------------------------- CUT HERE -----------------------------
Notice that to ensure that all files for Linda and Graham get to
their destination, David includes all 3 of Linda's valid addresses as well
as the one for Graham in his routing file. By doing this, regardless of
what address each of the other nodes has configured for Linda's system, all
of the files addressed to any of her addresses will be passed on to her
system. Since David knows that both Linda and Graham, use the SigNet
address for James, the FidoNet address for Eddie and AdultNet addresses for
everyone else, he doesn't need to include the other AKA addresses for all of
the other systems.
Now comes the largest of the 'hubs' in our scenario. If you've made
it this far, the following will be pretty straight forward. Since my
system is the 'central hub' for our scenario, it will have the largest of
the config files. My ROUTE.CFG file would look like this:
---------------------------- CUT HERE -----------------------------
*15:15/1
%15:100/250
#N
?15:100/250
?34:2416/0
?1:259/312
?15:400/100
?34:999/999
?1:255/999
?15:400/110
;
;
*15:15/1
%15:100/206
#N
?15:100/206
?10:10/11
;
;
*15:15/1
%15:610/300
#H
?15:610/300
?1:999/000
;
;
*34:3416/0
%25:4604/171
#N
?25:4604/171
?1:153/769
?1:153/709
---------------------------- CUT HERE -----------------------------
Since 3 of the 4 systems that receive their routed ISA files from
me have valid AdultNet addresses, I use my AdultNet address with the 'From'
operator. When sending files to James' system, I use my SigNet address so
that James' system will be able to recognize where the files came from
since he doesn't have an AdultNet address.
In each case, I include all of the AKA addresses for each of the
systems in my Route-For (? operator) line, this way regardless of what
address each of the systems uses, ALL files destined for their systems
(and/or downlinks) will be passed on to that system.
This concludes my 'tour' of ISA's File Routing features. Hopefully
I've explained enough here so that you will have a firm grasp of what is
needed/how ISA routes files between systems, however, if you are still
unsure, or have any questions not covered here, please feel free to contact
me via Netmail.
Jeff Bolton
AdultNet: 15:15/1
FidoNet: 1:250/517
SigNet: 34:3416/0
NOTE: In order to show the widest possible use of Multi-Zone
addresses, certain node addresses above have been changed to
suit the needs of these examples. Should you wish to contact
any of these people, please use a current nodelist to obtain
their proper addresses.